54.5K
Publications
2.9M
Citations
76.8K
Authors
8.4K
Institutions
Maintenance-Driven Software Engineering
1975 - 1983
During 1975–1983, software maintenance emerged as a central research and practice focus, with reliability measurement, time-dependent fault-detection modeling, and cross-model evaluation guiding dependability assessment across software systems. Maintainability and software quality factors gained formal prominence, yielding standardized development processes and lifecycle-oriented governance that shaped long-term software evolution. The period's discourse emphasized process-oriented design and principled engineering approaches, integrating error analysis and reliability testing as core evaluation techniques.
• Software reliability measurement and modeling matured as a central research paradigm, integrating execution-time validity, time-dependent error-detection rates, and cross-model evaluation to quantify reliability across software systems [1], [2], [3], [4], [6], [10], [11].
• Maintainability and software quality become core concerns, leading to formalized maintenance practices, quality factors, and standardized development processes that shape software lifecycle management [5], [12], [13], [16], [18], [20].
• Software engineering process, design, and re-engineering discourse emphasize process-oriented development, principled design, and methodological perspectives shaping practice and evaluation [7], [12], [17], [18], [20].
• Error analysis, fault detection, and reliability testing are formalized as core evaluation techniques, including analysis of errors in system programs, reliability testing methodologies, and reliability theory critiques [2], [3], [8], [9], [11], [14].
Software Evolution and Maintenance
1984 - 1994
Architecture-Driven Maintenance
1995 - 2001
Refactoring-Driven Evolutionary Maintenance
2002 - 2009
Metrics-Driven Maintenance Analytics
2010 - 2016
Repair-Driven Software Maintenance
2017 - 2023